Operating distributed computer systems

ABSTRACT

A system (e.g., one or more computer systems) of synchronous orchestration may store and/or replay one or more operations of a synchronous orchestration operation if one or more issues impair the synchronous orchestration operation. For example, the system may replay and/or reproduce a task of the synchronous orchestration operation after an amount of time transpires and/or after receiving a notification that indicates an impairment has been overcome. For instance, a replay and/or reproduction process to begin from a point where an orchestration layer was impaired. In one or more embodiments, one or more efforts in repeating an entire synchronous orchestration operation may be reduced.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/675,890 filed Aug. 14, 2017, by Kamaljeet Singh Bedi et al., andentitled “Operating Distributed Computer Systems,” which is incorporatedherein by reference.

TECHNICAL FIELD

Certain embodiments of this disclosure relate generally to processinginformation via distributed computer systems.

BACKGROUND

Networks allow users to access various types of computing resources,which may include hardware resources and/or software resources. Examplesof hardware resources include computer networks, servers, memory, and soon. Examples of software resources include applications, services, data,and so on. The computing resources may be used to process transactions.Data stores and databases can support various data types includingtraditional file, video, images, etc. within a name space leading to newopportunities and innovations. These data stores can have virtuallyunlimited storage capacity with extremely high durability andavailability along with low costs leading to widespread adoption.

SUMMARY

In one or more embodiments, a system (e.g., one or more computersystems) of synchronous orchestration may store and/or replay one ormore operations of a synchronous orchestration operation if one or moreissues impair the synchronous orchestration operation. For example, thesystem may replay and/or reproduce a task of the synchronousorchestration operation after an amount of time transpires and/or afterreceiving a notification that indicates an impairment has been overcome.For instance, a replay and/or reproduction process to begin from a pointwhere an orchestration layer was impaired may be utilized, which mayprovide one or more advantages over reinitiating a synchronousorchestration operation from its beginning and duplicating allsuccessful steps up to a point of failure. In one or more embodiments,reducing any repetition of steps of a synchronous orchestrationoperation may provide and/or implement one or more advantages. Forexample, retrying a failed transaction from a point of failure mayreduce repetition of one or more steps of a synchronous orchestrationoperation may provide and/or implement one or more advantages overrepeating the entire synchronous orchestration operation.

In one or more embodiments, one or more operations may involve multiplecomputer systems to perform one or more tasks (e.g., processes). Forexample, the computer systems operate via different platforms in aservice oriented architecture. In one or more embodiments, firstinformation may be received via multiple communicatively coupledcomputer systems. For example, the first information may be received bya computer system of the multiple communicatively coupled computersystems. In one or more embodiments, each of the multiplecommunicatively coupled computer systems may include one or morecomputer systems. The multiple communicatively coupled computer systemsmay process the first information in a synchronous fashion. For example,the multiple communicatively coupled computer systems may process thefirst information via a synchronous orchestration. In one or moreembodiments, second information, different from the first information,may be received via the multiple communicatively coupled computersystems. For example, the second information may be received by acomputer system of the multiple communicatively coupled computersystems.

In one or more embodiments, at least one communication issue between twoof the multiple communicatively coupled computer systems may bedetermined. For example, coupling the computer systems to perform theone or more tasks may pose one or more challenges. In one or moreembodiments, one or more of the computer systems and/or one or morenetworks, coupling two or more of the computer systems, may incur one ormore issues that may impair performing the one or more tasks. Forexample, the one or more issues may impair a synchronous orchestration.For instance, impairing a portion of a synchronous orchestration mayvoid an entire synchronous orchestration operation. In one or moreembodiments, an acknowledgement of receiving the second information maybe provided. For example, at least one of the multiple communicativelycoupled computer systems may provide the acknowledgement of receivingthe second information. In one or more embodiments, the acknowledgementmay be provided based at least on receiving the second informationand/or based at least on determining the at least one communicationissue.

In one or more embodiments, a first computer system of the at least tworespective communicatively coupled computer systems of the multiplecommunicatively coupled computer systems may perform a first process ofthe at least two different processes with the second information, whichmay produce first processed information, and the first computer systemmay store the first processed information. The first system may providethe first processed information to a second computer system, differentfrom the first computer system, of the at least two respective computersystems associated with a second process, different from the firstprocess, of the at least two different processes. In one or moreembodiments, the first system may provide the first processedinformation to the second computer system after a period of timetranspires. For example, the period of time may be associated with atleast one network delay. For instance, the at least one network delaymay include one or more of a network outage, network congestion, networkoverload, equipment failure, and a configuration error, among others.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsfeatures/advantages, reference is now made to the following description,taken in conjunction with the accompanying drawings, which are not drawnto scale, and in which:

FIG. 1 illustrates an exemplary computer system is illustrated,according to one or more embodiments;

FIG. 2A illustrates an example of computer systems coupled to a network,according to one or more embodiments;

FIG. 2B illustrates an example of computer systems coupled to multiplenetworks, according to one or more embodiments;

FIG. 3A illustrates an example of an envelope create orchestration,according to one or more embodiments;

FIG. 3B illustrates an example of a document orchestration, according toone or more embodiments;

FIG. 4 illustrates an example of an asynchronous flip process, accordingto one or more embodiments; and

FIG. 5 illustrates an example of a method of operating computer systems,according to one or more embodiments.

DETAILED DESCRIPTION

In the following description, details are set forth by way of example tofacilitate discussion of the disclosed subject matter. It should beapparent to a person of ordinary skill in the field, however, that thedisclosed embodiments are exemplary and not exhaustive of all possibleembodiments.

As used herein, a reference numeral followed by a letter refers to aspecific instance of an element and the numeral only form of thereference numeral refers to the collective element. Thus, for example,device ‘12A’ refers to an instance of a device class, which may bereferred to collectively as devices ‘12’ and any one of which may bereferred to generically as a device ‘12’.

In one or more embodiments, one or more systems that may be utilized inwith orchestration operations may be configured to accommodate one ormore delays and/or one or more error conditions that may occur duringexecution of the orchestration operations. For example, an orchestrationoperation may include multiple processes across multiple computersystems, and a delay or an error condition in communication between twocomputer systems of the multiple computer systems may occur. Forinstance, a first computer system of the two computer systems may storeresults of a process, due to a delay or an error condition incommunication, and provide the results of the process to a secondcomputer system of the two computer systems when the error condition isresolved or after a period of time transpires.

In one or more embodiments, one or more operations may involve multiplecomputer systems to perform one or more tasks (e.g., processes). Forexample, the computer systems may operate via different platforms in aservice oriented architecture. For instance, coupling the computersystems to perform the one or more tasks may pose one or morechallenges. In one or more embodiments, one or more of the computersystems and/or one or more networks, coupling two or more of thecomputer systems, may incur one or more issues that may impairperforming the one or more tasks. For example, the one or more issuesmay impair a synchronous orchestration. For instance, impairing aportion of a synchronous orchestration may void an entire synchronousorchestration operation.

In one or more embodiments, a system (e.g., a computer system) ofsynchronous orchestration may store and/or replay one or more operationsof a synchronous orchestration operation if one or more issues impairthe synchronous orchestration operation. For example, the system mayreplay and/or reproduce a task of the synchronous orchestrationoperation after an amount of time transpires and/or a notification, thatindicates an impairment has been overcome, is received. For instance, areplay and/or reproduction process to begin from a point where anorchestration layer was impaired. In one or more embodiments, one ormore efforts in repeating an entire synchronous orchestration operationmay be reduced.

Turning now to FIG. 1, an example of a computer system is illustrated,according to one or more embodiments. As shown, a computer system 1010may include a processor 1100, a volatile memory medium 1200, anon-volatile memory medium 1300, a network interface 1400, and aninput/output (I/O) subsystem 1500. As illustrated, volatile memorymedium 1200, non-volatile memory medium 1300, network interface 1400,and I/O subsystem 1500 may be communicatively coupled to processor 1100.

As shown, non-volatile memory medium 1300 may include an operatingsystem (OS) 1310, applications (APPs) 1320-1322, virtual machines (VMs)1330-1332, a hypervisor (HV) 1340, and containers 1350-1352. In one ormore embodiments, one or more of OS 1310, APPs 1320-1322, VMs 1330-1332,HV 1340, and containers 1350-1352 may include instructions executable byprocessor 1100. In one example, processor 1100 may execute instructionsof one or more of OS 1310, APPs 1320-1322, VMs 1330-1332, HV 1340, andcontainers 1350-1352 via non-volatile memory medium 1300. In anotherexample, one or more portions of the instructions of the one or more ofOS 1310, APPs 1320-1332, VMs 1330-1332, HV 1340, and containers1350-1352 may be transferred to volatile memory medium 1200, andprocessor 1100 may execute the one or more portions of the instructionsof the one or more of OS 1310, APPs 1320-1332, VMs 1330-1332, HV 1340,and containers 1350-1352 via volatile memory medium 1200.

In one or more embodiments, HV 1340 may include one or more of software,firmware, and hardware that creates and executes one or more VMs (e.g.,one or more of VMs 1330-1332). For example, computer system 1010 may beconsidered host machine when HV 1340 executes and one or more of VMs1330-1332 are executed via HV 1340. For instance, a virtual machine (VM)(e.g., a VM of VMs 1330-1332) may be considered a guest machine. In oneor more embodiments, a VM may provide one or more structures and/orfunctionalities as those described with reference to computer system1010 (e.g., singularly or via nesting of hypervisors and virtualmachines). In one example, the VM may provide emulated devices to aguest OS that executes via the VM. In another example, the VM mayprovide hardware devices to the guest OS that executes via the VM. Inone instance, the guest OS may access hardware in a pass-throughconfiguration. In another instance, the guest OS may access hardware ina single root input/output virtualization (SR-MY) configuration. In oneor more embodiments, guest operating systems may share one or moredevices of a host machine. For example, the guest operating systems mayshare one or more of a network adapter via virtual network adapters anda storage device via a virtual storage devices (e.g., virtual disks,virtual memory, etc.), among others.

In one or more embodiments, OS level virtualization may be utilized. Forexample, OS level virtualization may include a kernel of an OS thatpermits multiple isolated user space instances of collections ofprocesses (e.g., programs, applications, services, etc.). For instance,these instances are often referred to as “containers”, “softwarecontainers”, “virtualization engines”, or “jails” (e.g., FreeBSD jails,chroot jails, etc.). In one or more embodiments, with OS levelvirtualization, an OS may behave and/or may appear like multipledifferent, individual computer systems. For example, little to nooverhead may be imposed by OS level virtualization, as processes in OSlevel virtual partitions may utilize a single system call interface ofan OS. For instance, OS level virtual partitions may not be subjected toemulation or be executed via virtual machines. In one or moreembodiments, OS level virtualization may be utilized in consolidatingcomputer system hardware or virtual machines by moving services onseparate hosts or virtual machines into containers on a computer systemor single virtual machine.

In one or more embodiments, a container may be or include software in afile system that includes one or more of instructions executable by aprocessor (e.g., a program, software, an application, server software, aservice, etc.), one or more runtime libraries, one or more system tools,and one or more system libraries, among others. For example, a containermay be or include a Docker container, a LXC, or a Kubernetes pod, amongothers. In one or more embodiments, a container may provide and/or mayimplement operating system-level virtualization via a virtualenvironment that includes a separate process space and/or a separatenetwork space, rather than creating and/or implementing a virtualmachine.

In one or more embodiments, a container may be or include a pod (e.g., aKubernetes pod). For example, a pod may provide and/or add a higherlevel of abstraction to one or more containerized elements. Forinstance, a pod may include one or more containers that may be warrantedto be co-located and/or executed on a computer system (e.g., a hostcomputer system, host machine, etc.) and may share resources of thecomputer system. In one or more embodiments, a thick container may be orinclude a pod, and a thin container may include a single container.

In one or more embodiments, containers may provide and/or offer animmutable quality and/or option. For example, a container may bedeployed, destroyed, modified, re-constructed and/or re-created, andre-deployed. In one instance, instructions, executable by a processor,of a container may not be modified while the container is executing. Inanother instance, instructions, executable by a processor, of acontainer may not be modified once the container is created.

In one or more embodiments, the term “memory medium” may mean a “memorydevice”, a “memory”, a “storage device”, a “tangible computer readablestorage medium”, and/or a “computer-readable medium”. In one example, amemory medium may be a volatile memory medium. For instance, thevolatile memory medium may lose stored data when the volatile memorymedium no longer receives power. In a second example, a memory mediummay be a non-volatile memory medium. For instance, the non-volatilememory medium may not lose stored data when the volatile memory mediumno longer receives power or when power is not applied. In anotherexample, a memory medium may include a volatile memory medium and anon-volatile memory medium.

In one or more embodiments, a volatile memory medium may includevolatile storage. For example, the volatile storage may include randomaccess memory (RAM), dynamic RAM (DRAM), static RAM (SRAM), and/orextended data out RAM (EDO RAM), among others. In one or moreembodiments, a non-volatile memory may include non-volatile storage. Forexample, the non-volatile storage may include read only memory (ROM),programmable ROM (PROM), erasable PROM (EPROM), electrically erasablePROM (EEPROM), a magnetic storage medium (e.g., a hard drive, a floppydisk, a magnetic tape, etc.), ferroelectric RAM (FRAM), flash memory, asolid state drive (SSD), non-volatile RAM (NVRAM), a one-timeprogrammable (OTP) memory, and/or optical storage (e.g., a compact disc(CD), a digital versatile disc (DVD), a BLU-RAY disc (BD), etc.), amongothers.

In one or more embodiments, I/O subsystem 1500 may include or representa variety of communication interfaces, graphics interfaces, videointerfaces, user input interfaces, and/or peripheral interfaces, amongothers. For example, I/O subsystem 1500 may include one or more of atouch screen, a display, a display adapter, and a universal serial bus(USB) interface, among others. For instance, a touch screen may includecircuitry that enables touch functionality in conjunction with a displaythat is driven by a display adapter.

In one or more embodiments, network interface 1400 may be configured tobe coupled to a network. For example, network interface 1400 may permitcomputer system 1010 to be communicatively coupled to a network. In oneinstance, network interface 1400 may be configured to be coupled to awired network. In a second instance, network interface 1400 may beconfigured to be coupled to a wireless network. In a second instance,network interface 1400 may be configured to be coupled to an opticalnetwork.

In one or more embodiments, one or more of volatile memory medium 1200,non-volatile memory medium 1300, network interface 1400, and I/Osubsystem 1500 may be communicatively coupled to processor 1100 via oneor more buses. For example, a bus may include one or more of aperipheral component interconnect (PCI) bus, a serial peripheralinterface (SPI) bus, an inter-integrated circuit (I²C) bus, an enhancedserial peripheral interface (eSPI) bus, a system management bus (SMBus),a universal serial bus, and a low pin count (LPC) bus, among others. Inone or more embodiments, one or more of volatile memory medium 1200,non-volatile memory medium 1300, network interface 1400, and I/Osubsystem 1500 may be communicatively coupled to processor 1100 via oneor more of a PCI-Express (PCIe) root complex and one or more PCIeswitches, among others.

In one or more embodiments, processor 1100 may execute instructions inimplementing one or more systems, flowcharts, methods, and/or processesdescribed herein. In one example, processor 1100 may execute processorinstructions from one or more of memory media 1200 and 1300 inimplementing one or more systems, flowcharts, methods, and/or processesdescribed herein. In another example, processor 1100 may executeinstructions received via network interface 1400 in implementing one ormore systems, flowcharts, methods, and/or processes described herein.

In one or more embodiments, processor 1100 may include circuitry thatmay interpret and/or execute program instructions and/or process data,among others. For example, processor 1100 may include one or more of asystem, a device, and an apparatus that may interpret and/or executeprogram instructions and/or process data, among others. For instance,processor 1100 may include one or more of a central processing unit(CPU), a microprocessor, a graphics processing unit (GPU), anapplication processor, a digital signal processor (DSP), and anapplication specific integrated circuit (ASIC), among others.

Turning now to FIG. 2A, computer systems coupled to a network areillustrated, according to one or more embodiments. As shown, computersystems 1010A-1010H may be communicatively coupled to a network 2010. Inone or more embodiments, network 2010 may include one or more of a wirednetwork, an optical network, and a wireless network. For example,network 2010 may include one or more of a local area network (LAN), awide area network (WAN), a wireless LAN (WLAN), a metropolitan areanetwork (MAN), a public switched telephone network (PSTN), a public WAN(e.g., an Internet), a private WAN, a cellular telephone network, asatellite telephone network, and a virtual private network (VPN), amongothers. In one or more embodiments, network 2010 may be coupled to oneor more other networks. For example, network 2010 may be coupled to oneor more of a LAN, a WAN, a WLAN, a MAN, a PSTN, a public WAN, a privateWAN, a cellular telephone network, a satellite telephone network, and aVPN, among others.

Turning now to FIG. 2B, computer systems coupled to various networks areillustrated, according to one or more embodiments. As shown, computersystems 1010A-1010C may be coupled to a network 2010A. In one or moreembodiments, one or more users may operate one or more of computersystems 1010A-1010C. For example, the one or more users may be one ormore customers. For instance, the one or more customers may utilize oneor more of computer systems 1010A-1010C for one or more transactions.

As illustrated, computer system 1010D may be coupled to network 2010Aand a network 2010B; computer system 1010E may be coupled to network2010B and a network 2010C; computer system 1010F may be coupled tonetwork 2010C and a network 2010D; computer system 1010G may be coupledto network 2010D and a network 2010E; and computer system 1010H may becoupled to network 2010E.

In one or more embodiments, two of more of computer systems 1010D-1010Hmay be configured to provide a service oriented architecture. In oneexample, two or more of computer systems 1010D-1010H may be configuredto provide respective one or more services of the service orientedarchitecture. In one instance, a first computer system of computersystems 1010D-1010H may be configured to provide a service of theservice oriented architecture. In another instance, a second computersystem, different from the first computer system, of computer systems1010D-1010H may be configured to provide one or more services of theservice oriented architecture. In another example, a service within aservice oriented architecture may be or include a discrete unit offunctionality. In one instance, the service may be accessed remotely. Inanother instance, the service may be acted upon and/or updatedindependently.

In one or more embodiments, a service oriented architecture may includeone or more attributes. In one example, an attribute of the serviceoriented architecture may be or include a logical representation of abusiness activity. For instance, the business activity may be associatedwith one or more specific outcomes. In a second example, an attribute ofthe service oriented architecture may be or include a self-containment.In a third example, an attribute of the service oriented architecturemay be or include an opacity. For instance, the service orientedarchitecture may be a “black box” for and/or to its consumers. Inanother example, an attribute of the service oriented architecture maybe or include one or more underlying services. In one or moreembodiments, one or more services of a service oriented architecture maybe utilized in providing one or more functionalities of an application.For example, the application may be or include a software application.In one instance, the software application may be distributed between oramong two or more computer systems. In another instance, the softwareapplication may be loosely coupled between or among two or more computersystems

In one or more embodiments, services of a service oriented architecturemay utilize one or more protocols that describe how data is transferredfrom one service to another service and/or that describe how data isparsed, utilizing description metadata. For example, a data descriptionlanguage may be utilized. In one instance, the data description languagemay be or include a markup language (e.g., a hypertext markup language(HTML), an extensible markup language (XML), etc.). In another instance,the data description language may be or include a JavaScript objectnotation (JSON). In one or more embodiments, the metadata may describeone or more functional characteristics of a service and/or may describeone or more characteristics of one or more qualities of service, amongothers.

Turning now to FIG. 3A, an example of an envelope create orchestrationis illustrated, according to one or more embodiments. In one or moreembodiments, two or more of computer systems 1010D-1010G may perform oneor more orchestration tasks. In one or more embodiments, an event hub3020 may receive a document (e.g., an eDocument) from computer system3010A. For example, computer system 1010D may include event hub 3020. Inone or more embodiments, if event hub 3020 receives more documents thatit may process in a period of time, event hub 3020 may store documentsvia a queue backup 3030. For example, event hub 3020 may retrievedocuments from queue backup 3030, when a processing load permits, andprocess the retrieved documents.

In one or more embodiments, an enterprise document service layer 3030may receive a document (e.g., an eDocument) and may combine the documentwith an envelope. In one example, the envelope may include one or morecustomer attributes (e.g., a name, an address, an email address, atelephone number, an identification number, etc.), which may be combinedwith a document (e.g., an eDocument). In another example, the envelopemay include one or more names of people (e.g., recipients) that need tosign an eDocument. In one or more embodiments, enterprise documentservice layer 3030 may create an envelope/document combination forsigning. As illustrated, computer system 1010E may include enterprisedocument service layer 3030.

In one or more embodiments, enterprise document service layer 3030 mayattempt to provide an envelope/document combination to an enterprisedocument storage 3050. If enterprise document service layer 3030 is notsuccessful in providing the envelope/document combination to enterprisedocument storage 3050, enterprise document service layer 3030 mayutilize an asynchronous flip process 3040A. For example, asynchronousflip process 3040A may store the envelope/document combination and mayattempt to provide the envelope/document combination after a period oftime transpires. For instance, providing the envelope/documentcombination after the period of time transpires may include a replay ofthe attempt to provide the envelope/document combination to enterprisedocument storage 3050.

In one or more embodiments, enterprise document storage 3050 may receivean envelope/document combination and attempt to store theenvelope/document combination to a storage 3060. As illustrated,computer system 1010G may include storage 3060. If enterprise documentstorage 3050 is not successful in storing the envelope/documentcombination to storage 3060, enterprise document storage 3050 mayutilize an asynchronous flip process 3040B. For example, asynchronousflip process 3040B may store the envelope/document combination and mayattempt to store the envelope/document combination after a period oftime transpires. For instance, storing the envelope/document combinationafter the period of time transpires may include a replay of the attemptto store the envelope/document combination to storage 3060. In one ormore embodiments, storage 3060 may be or include a database.

Turning now to FIG. 3B, an example of a document orchestration isillustrated, according to one or more embodiments. In one or moreembodiments, two or more of computer systems 1010H-1010L may perform oneor more orchestration tasks. In one or more embodiments, a callback 3105may be received by an event hub 3110. In one example, callback 3105 mayinclude delivery information. For instance, the delivery information mayindicate that a document (e.g., an eDocument) has been emailed to arecipient of the document. In a second example, callback 3105 mayinclude commencement information. In one instance, the commencementinformation may indicate that a recipient of the document has opened thedocument. In another instance, the commencement information may indicatethat a recipient of the document has opened an envelope associated withthe document. In another example, callback 3105 may include signatureinformation. In one instance, the signature information may include aneSignature. In another instance, the signature information may include adocument ID (e.g., a document ID that may correspond to an eSignature).In one or more embodiments, callback 3105 may include an envelope and/orany information associated with an envelope.

In one or more embodiments, if event hub 3110 receives more callbacksthat it may process in a period of time, event hub 3110 may storerequests via a queue backup 3120. For example, event hub 3110 mayretrieve one or more callbacks 3105 from queue backup 3120, when aprocessing load permits, and process the callbacks. In one or moreembodiments, event hub 3110 may provide callback 3105 to a documentretrieval service 3130. For example, document retrieval service 3130 mayretrieve a document (e.g., an eDocument) from a document storageservice. For instance, the document storage service may be an eDocumentservice like or such as Docusign, among others.

In one or more embodiments, document retrieval service 3130 may attemptto provide a document to a status updater 3150. If document retrievalservice 3130 is not successful in providing the document to statusupdater 3150, document retrieval service 3130 may utilize anasynchronous flip process 3140A. For example, asynchronous flip process3140A may store the document and may attempt to provide the documentafter a period of time transpires. For instance, providing the documentafter the period of time transpires may include a replay of the attemptto provide the document to status updater 3150.

In one or more embodiments, an asynchronous flip process 3140 may beperformed automatically. For example, asynchronous flip process 3140 maybe performed in response to an unsuccessful deliver of information fromone computer system to another computer system. For instance, there maybe no manual intervention in performing asynchronous flip process 3140.In one or more embodiments, asynchronous flip process 3140 may beperformed until information is successfully transferred from onecomputer system to another computer system. For example, replayingand/or reproducing a task of a synchronous orchestration operation untilinformation is successfully transferred from one computer system toanother computer system may permit a service level agreement (SLA)associated with a synchronous orchestration to be achieved and/oraccomplished.

In one or more embodiments, status updater 3150 may update a status of adocument (e.g., a document retrieved via the eDocument service). Forexample, updating a status of a document may include updating a versionof a document. For instance, updating a status of a document may includecreating a new version of the document. In one or more embodiments,multiple versions of the document may be created. For example, a versionof the multiple versions of the document may be associated with asignature of a person signing the document. For instance, a version maybe created for each person signing the document.

In one or more embodiments, status updater 3150 may attempt to providean envelope/document combination to a document updater 3160. If statusupdater 3150 is not successful in providing the envelope/documentcombination to document updater 3160, status updater 3150 may utilize anasynchronous flip process 3140B. For example, asynchronous flip process3140B may store the envelope/document combination and may attempt toprovide the envelope/document combination after a period of timetranspires. For instance, providing the envelope/document combinationafter the period of time transpires may include a replay of the attemptto provide the envelope/document combination to document updater 3160.In one or more embodiments, document updater 3160 may update a signedversion of a document with metadata. For example, the metadata mayinclude information, such as what type of document, a number of pages ofthe document, version information, etc.

In one or more embodiments, document updater 3160 may attempt to storethe updated document to a storage 3170. As illustrated, computer system1010L may include storage 3170. If document updater 3160 is notsuccessful in storing the updated document to storage 3170, documentupdater 3160 may utilize an asynchronous flip process 3140C. Forexample, asynchronous flip process 3140C may store the updated documentand may attempt to store the updated document after a period of timetranspires. For instance, storing the updated document after the periodof time transpires may include a replay of the attempt to store theupdated document to storage 3170. In one or more embodiments, storage3170 may be or include a database.

Turning now to FIG. 4, an asynchronous flip process is illustrated,according to one or more embodiments. At 4010, information associatedwith a transmission may be received. For example, the transmission maybe from a first computer system to a second computer system. In one ormore embodiments, the information associated with the transmission mayinclude a message and error information. For example, the errorinformation may include information associated with an error intransmitting the message from the first computer system to the secondcomputer system. For instance, the error in transmitting the messagefrom the first computer system to the second computer system may includeone or more of a network delay, a network outage, network congestion,network overload, equipment failure, and a configuration error, amongothers. At 4020, the error information may be stored. For example, theerror information may be associated with the transmission. For instance,the error information may be stored via a database. At 4030, the messagemay be stored. In one example, the message may be stored via a queue. Inanother example, the message may be stored via a database.

At 4040, the message may be retrieved. In one example, the message maybe retrieved via a queue. In another example, the message may beretrieved via a database. In one or more embodiments, an amount of timemay transpire before the message may be retrieved. In one example, theamount of time may be predetermined. For instance, a countdown clock mayexpire before the message may be retrieved. In another example,information may be received that indicates that the message may beretrieved. In one instance, the information that may be received thatindicates that the message may be retrieved may include an indicationthat an error condition has been voided and/or fixed. In anotherinstance, the information that may be received that indicates that themessage may be retrieved may include an indication communications withthe second computer system is possible and/or permitted.

At 4050, the message may be provided. For example, the message may beprovided to the second computer system. In one or more embodiments,providing the message may include a performing replay process. Forexample, the message may be provided to the second computer system in afashion as or similar to a first time the message was attempted to beprovided to the first computer system.

Turning now to FIG. 5, an example of a method of operating computersystems is illustrated, according to one or more embodiments. At 5010,first information may be received via multiple communicatively coupledcomputer systems. For example, the first information may be received bya computer system of the multiple communicatively coupled computersystems. In one or more embodiments, each of the multiplecommunicatively coupled computer systems may include one or morecomputer systems. For example, the one or more computer systems mayinclude one or more functionalities and/or one or more structures asthose described with reference to computer system 1010. In one or moreembodiments, the multiple communicatively coupled computer systems maybe configured to provide a service oriented architecture that includesat least two different processes associated with at least two respectivecommunicatively coupled computer systems of the multiple communicativelycoupled computer systems.

At 5020, the multiple communicatively coupled computer systems mayprocess the first information in a synchronous fashion. For example, themultiple communicatively coupled computer systems may process the firstinformation via a synchronous orchestration. At 5030, secondinformation, different from the first information, may be received viathe multiple communicatively coupled computer systems. For example, thesecond information may be received by a computer system of the multiplecommunicatively coupled computer systems.

At 5040, at least one communication issue between two of the multiplecommunicatively coupled computer systems may be determined. In oneexample, it may be determined that the two of the multiplecommunicatively coupled computer systems may not be able to communicateinformation. For instance, a first computer system of the two of themultiple communicatively coupled computer systems may determine that thetwo of the multiple communicatively coupled computer systems may not beable to communicate information. In another example, it may bedetermined that the two of the multiple communicatively coupled computersystems may not be able to communicate information at a sufficientcommunication rate. For instance, it may be determined that the two ofthe multiple communicatively coupled computer systems may not be able tocommunicate information at a sufficient communication rate that maypermit a synchronous orchestration of processing.

At 5050, an acknowledgement of receiving the second information may beprovided. For example, at least one of the multiple communicativelycoupled computer systems may provide the acknowledgement of receivingthe second information. In one instance, the at least one of themultiple communicatively coupled computer systems may provide theacknowledgement of receiving the second information to a computer system(e.g., a computer system of computer systems 1010A-1010C) that providedthe second information. In another instance, the first computer systemof the two of the multiple communicatively coupled computer systems maydetermine that the two of the multiple communicatively coupled computersystems may provide the acknowledgement of receiving the secondinformation to a computer system (e.g., a computer system of computersystems 1010A-1010C) that provided the second information. In one ormore embodiments, the acknowledgement may be provided based at least onreceiving the second information and/or based at least on determiningthe at least one communication issue.

At 5060, the first computer system of the at least two respectivecommunicatively coupled computer systems of the multiple communicativelycoupled computer systems may perform a first process of the at least twodifferent processes with the second information, which may produce firstprocessed information. In one example, computer system 1010D may performthe first process of the at least two different processes with thesecond information, which may produce the first processed information.In another example, computer system 1010J may perform the first processof the at least two different processes with the second information,which may produce the first processed information.

At 5070, the first computer system may store the first processedinformation. In one example, computer system 1010D may store the firstprocessed information. In another example, computer system 1010J maystore the first processed information. In one instance, the firstcomputer system may store the first processed information for at least aperiod of time. In another instance, the first computer system may storethe first processed information via a queue. In one or more embodiments,the first computer system may store the first processed informationbased at least on or in response to determining the at least onecommunication issue.

At 5080, the first system may provide the first processed information toa second computer system, different from the first computer system, ofthe at least two respective computer systems of the multiplecommunicatively coupled computer systems associated with a secondprocess, different from the first process, of the at least two differentprocesses. In one example, computer system 1010D may provide the firstprocessed information to computer system 1010E. For instance, computersystem 1010D may provide the first processed information to computersystem 1010E via network 2010B. In one example, computer system 1010Jmay provide the first processed information to computer system 1010K.For instance, computer system 1010J may provide the first processedinformation to computer system 1010J via a network. In another example,the second information may include a signature. For instance, thesignature may be or include an eSignature.

In one or more embodiments, the first computer system may provide thefirst processed information to the second computer system after a periodof time transpires. For example, the period of time may be associatedwith at least one network delay. For instance, the at least one networkdelay may include one or more of a network outage, network congestion,network overload, equipment failure, and a configuration error, amongothers. In one or more embodiments, the first computer system may storethe first processed information via a queue, and the first computersystem may dequeue the processed information and may provide the firstprocessed information to the second computer system. For example, thefirst computer system may dequeue the first processed information afterthe period of time transpires.

In one or more embodiments, one or more of the method and/or processelements and/or one or more portions of a method and/or processorelements may be performed in varying orders, may be repeated, or may beomitted. Furthermore, additional, supplementary, and/or duplicatedmethod and/or process elements may be implemented, instantiated, and/orperformed as desired, according to one or more embodiments. Moreover,one or more of system elements may be omitted and/or additional systemelements may be added as desired, according to one or more embodiments.

In one or more embodiments, a memory medium may be and/or may include anarticle of manufacture. For example, the article of manufacture mayinclude and/or may be a software product and/or a program product. Forinstance, the memory medium may be coded and/or encoded withprocessor-executable instructions in accordance with one or moreflowcharts, systems, methods, and/or processes described herein toproduce the article of manufacture.

The above disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments which fall within thetrue spirit and scope of the present disclosure. Thus, to the maximumextent allowed by law, the scope of the present disclosure is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

What is claimed is:
 1. A system, comprising: a plurality ofcommunicatively coupled computer systems, configured to: provide atleast two different processes associated with at least two respectivecomputer systems of the plurality of communicatively coupled computersystems, wherein the at least two different processes form a synchronousorchestration operation; receive first information by each of theplurality of communicatively coupled computer systems; process the firstinformation in a synchronous fashion by each of the plurality ofcommunicatively coupled computer systems; and receive second informationby each of the plurality of communicatively coupled computer systems,wherein the second information is different from the first information;wherein the plurality of communicatively coupled computer systemscomprises: a first computer system and a second computer system, thefirst computer system configured to: perform a first process of the atleast two different processes with the second information, to producefirst processed information; determine that the first computer systemcannot communicate with the second computer system based at least inpart upon a communication issue that is associated with a period oftime, wherein the communication issue impairs one or more operations ofthe synchronous orchestration; store the first processed information inresponse to determining the communication issue; and provide, after theperiod of time transpires, the first processed information to the secondcomputer system, wherein:  the second computer system is different fromthe first computer system;  the second computer system is associatedwith a second process of the at least two different processes in thesynchronous orchestration operation; and  the second process isdifferent from the first process; and the second computer systemconfigured to: perform the second process with the first processedinformation.
 2. The system of claim 1, wherein the period of time isassociated with at least one network delay.
 3. The system of claim 1,wherein the second information includes a signature.
 4. The system ofclaim 1, wherein the first computer system is further configured tostore the first processed information for at least the period of time.5. The system of claim 4, wherein, to store the first processedinformation for at least the period of time, the first computer systemis further configured to store the first processed information via aqueue; and wherein the first computer system is further configured todequeue the first processed information after the period of timetranspires.
 6. A method, comprising: providing, by a plurality ofcommunicatively coupled computer systems, at least two differentprocesses associated with at least two respective computer systems ofthe plurality of communicatively coupled computer systems, wherein theat least two different processes form a synchronous orchestrationoperation; receiving, by each of the plurality of communicativelycoupled computer systems, first information; processing, by each of theplurality of communicatively coupled computer systems, the firstinformation in a synchronous fashion; receiving, by each of theplurality of communicatively coupled computer systems, secondinformation, wherein the second information is different from the firstinformation; performing, by a first computer system of the plurality ofcommunicatively coupled computer systems, a first process of the atleast two different processes with the second information, producingfirst processed information; determining that the first computer systemcannot communicate with the second computer system based at least inpart upon a communication issue that is associated with a period oftime, wherein the communication issue impairs one or more operations ofthe synchronous orchestration; storing the first processed informationin response to determining the communication issue; providing, by thefirst computer system, the first processed information to the secondcomputer system after the period of time transpires, wherein: the secondcomputer system is different from the first computer system; the secondcomputer system is associated with a second process of the at least twodifferent processes in the synchronous orchestration operation; and thesecond process is different from the first process; and performing, bythe second computer system, the second process with the first processedinformation.
 7. The method of claim 6, wherein the period of time isassociated with at least one network delay.
 8. The method of claim 6,wherein the second information includes a signature.
 9. The method ofclaim 6, further comprising: storing, by the first computer system, thefirst processed information for at least the period of time.
 10. Themethod of claim 9, wherein storing the first processed informationincludes storing the first processed information via a queue; and themethod further comprises after the period of time transpires, dequeuing,by the first computer system, the first processed information.
 11. Acomputer-readable non-transitory memory medium that comprisesinstructions executable by communicatively coupled processors of asystem, wherein when the processors execute the instructions, theinstructions cause the system to: provide at least two differentprocesses associated with at least two respective processors of thesystem, wherein the at least two different processes form a synchronousorchestration operation; receive first information by each of theplurality of communicatively coupled computer systems; process the firstinformation in a synchronous fashion by each of the plurality ofcommunicatively coupled computer systems; and receive second informationby each of the plurality of communicatively coupled computer systems,wherein the second information is different from the first information;wherein, when a first processor of the at least two respectiveprocessors executes the instructions, the system is further caused to:perform a first process of the at least two different processes with thesecond information, to produce first processed information; determinethat the first computer system cannot communicate with the secondcomputer system based at least in part upon a communication issueassociated with a period of time, wherein the communication issueimpairs one or more operations of the synchronous orchestration; storethe first processed information in response to determining thecommunication issue; provide, after the period of time transpires, thefirst processed information to the second processor, different from thefirst processor, of the at least two respective processors of the systemassociated with a second process, different from the first process, ofthe at least two different processes; wherein: the second processor isdifferent from the first processor; the second processor is associatedwith a second process of the at least two different processes in thesynchronous orchestration operation; and the second process is differentfrom the first process; and wherein, when the second processor of the atleast two respective processors executes the instructions, the system isfurther caused to perform the second process with the first processedinformation.
 12. The computer-readable non-transitory memory medium ofclaim 11, wherein the period of time is associated with at least onenetwork delay.
 13. The computer-readable non-transitory memory medium ofclaim 11, wherein the second information includes a signature.
 14. Thecomputer-readable non-transitory memory medium of claim 11, furthercomprising instructions that, when executed by the first processor,cause the system to store the first processed information at least theperiod of time.
 15. The computer-readable non-transitory memory mediumof claim 11, wherein storing the first processed information comprisesstoring the first processed information via a queue; and furthercomprising instructions that, when executed by the first processor,cause the system to dequeue the first processed information after theperiod of time transpires.